fix: inline commits into nextjs-tracker prompt to stop codebase exploration#693
Merged
southpolesteve merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
The agent kept launching a Task subagent to "explore the vinext codebase structure" despite instructions not to, consuming the entire 30-minute timeout. The task permission deny in the agent config was not effective. Fix: embed the commits JSON directly into the prompt so the agent has all data immediately and no reason to explore. Also add explicit "do not explore, do not launch subagents" at the end of the prompt.
commit: |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
task: "*": denypermission and the "Do NOT explore" instruction, spending 28 of 30 minutes on a Task subagent exploring the local codebase before looking at a single commitPrevious failed runs:
Both timed out because the agent launched an explore subagent that ran for ~28 minutes.